FOUR-32946 Improve the API /api/1.0/processes - #9056

Issue & Reproduction Steps

Improve the API /api/1.0/processes

Solution

• Improves the performance of GET /api/1.0/processes by moving pagination into the database and eliminating unnecessary per-process work.
• Previously, the endpoint loaded the entire matching process collection, including large BPMN/SVG fields and event data, performed enrichment across every matching process, and only then converted the collection into a paginator. As the number of processes increased, response time and query work increased even when the requested page size remained unchanged.
• The endpoint now applies filtering, sorting, and pagination in SQL before serializing or enriching the requested page.

Related Tickets & Packages

FOUR-32946

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:deploy